Asset Information Requirements (AIR) define the specific information needed about assets to support their ongoing operation, maintenance, and long-term management. These requirements are essential for enabling informed decision-making throughout the asset lifecycle from handover to replacement or refurbishment.
AIR is typically developed at the early stages of a project to ensure that critical operational data is identified in advance and delivered during design and construction.
AIR should be defined by or on behalf of the Appointing Party (or by a Representative, Advisor or Consultant that we have appointed). It can be developed in collaboration with Facilities Management (FM) teams, asset managers, or specialist advisors to ensure that delivered information genuinely supports operational use.
As per ISO 19650-2, Clause 5.2.1, the AIR is part of our Exchange Information Requirements (EIR) and must be clearly defined if the project supports operational use.
In this document, we’re not focusing on structured data such as IFC and COBie mappings, file formats, verification rules, and delivery assignments yet; that happens in the Scope module (Docs + Scope).
This AIR document serves as a planning tool to identify what operational data we need, why, and how we’ll use it.
When we set our AIR early in the project, we help the delivery team understand:
This improves the way information is structured, tracked, and validated during the project. It also reduces the risk of missing or inconsistent data at the end.
While our structured AIR including IFC and COBie mappings, verification rules, and delivery assignments will be created in the Plannerly Scope module (Docs + Scope).
This AIR document serves as a planning tool to identify what operational data we need, why, and how we’ll use it.